fix(deep-scan): preserve convergence across alias consolidation - #762
fix(deep-scan): preserve convergence across alias consolidation#762Hughhhhcoder wants to merge 3 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
…lineage-convergence # Conflicts: # plugins/codex-security/mcp-app/src/deep-scan/artifact-validation.ts
|
Updated this branch with a normal merge commit ( Validation on the merged tree:
No force-push was used. |
|
@codex review |
|
Codex Review: Didn't find any major issues. You're on a roll. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
…lineage-convergence
|
I refreshed this branch with the latest Validation after the update:
The focused regression coverage still exercises discovery validation, reducer validation, lineage convergence, and empty-artifact handling. |
Summary
Fixes #711.
Deep Scan used canonical finding identity to derive novelty, so consolidating semantically equivalent findings under one retained source lineage could be counted as a new finding and reset no-new convergence.
Changes
Testing
npx --yes pnpm@11.9.0 --dir ../../plugins/codex-security/mcp-app run test:mcp— 23/23 test files passed after building the bundled plugin.npx --yes pnpm@11.9.0 run typecheck— passed.uvx --from ruff==0.16.1 ruff check --config plugins/codex-security/pyproject.toml .github/scripts/check_plugin_source_compatibility.py .github/scripts/test_check_plugin_source_compatibility.py plugins/codex-security— passed.uvx --from ruff==0.16.1 ruff format --check --config plugins/codex-security/pyproject.toml .github/scripts/check_plugin_source_compatibility.py .github/scripts/test_check_plugin_source_compatibility.py plugins/codex-security— passed.python .github/scripts/check_plugin_source_compatibility.py— passed.git diff --check— passed.The local SDK install emitted an engine warning because Node v25.4.0 is outside the declared Node 22/24/26 ranges; all listed checks still passed.
Risk and rollout
This changes internal convergence accounting only; it does not change a public API or artifact schema. Existing source-accounting checks remain in place, split/ambiguous lineage remains a hard error, and legacy artifacts retain exact-identity behavior. CI on a supported Node version provides the rollout gate.
Public disclosure review